High Availability

---

High Availability

SyncNow enterprise edition supports establishing a cluster of SyncNow cluster.SyncNow cluster is a group of nodes in an active-active form. SyncNow requests are queued, and every node can get a sync or devops request and process it. SyncNow cluster enables the continuation of Synchronizations and DevOps gate processes even if one or more nodes fails.

Architecture

SyncNow cluster consists of at least two nodes. Every cluster has a main server which is elected if one of the nodes fails. The main server executes unique processes, for example – purging jobs, and sync template processing. SyncNow stores all the work in queue, every node can fetch requests from the queue and process them. The queue can be viewed from SyncNow User Interface.

Load Balancer

A load balancer is the one that transfer HTTP requests to every node.

App Nodes and Number of Nodes

SyncNow Enterprise app instance. This can be in the form of a docker or app deployed on Linux | Windows systems. All nodes should be connected to the same database. SyncNow does not store any important information inside app nodes.

The minimal number for High Availability is two SyncNow nodes.

Database

Database in a cluster active-passive configuration. We support SQL Server Clusters and PostrgreSQL cluster.

Cloud Native

We do not test all cloud native scenarios on a regular basis. SyncNow was tested with AWS EKS and Azure AKS in the past. Contact us if you have questions on more deployment options.

Failures and Recovery

SyncNow cluster can automatically recover from failures.

1. Nodes identify whether there is a main node that has failed, or a new one will be elected.
2. If one of the nodes fails, another will node will take over its operations.
3. The cluster can grow and automatically split tasks to multiple nodes.

Cluster View and Operations

1. Go to the App Instances page.
2. Star 2 shows the current main app instance. Main instance executes purge cycling jobs.
3. Star 3 shows the calculated main instance. If a calculated main instance is not operational, then it elects a new main instance. However, as soon as the calculated main instance will become again operational, it will become main.